Make bearer cookie name configurable #25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's meant to be used by the client for requests to the server, sending it from the server makes no sense. Signed-off-by: Roman Khimov <[email protected]>
Sometimes it's harmful to attach "Bearer" cookie (automatically used by the gateway) to all of the browser requests. Using some alternative name like "X-Bearer" makes it possible for the frontend to decide which requests are made with which headers. Signed-off-by: Roman Khimov <[email protected]>
roman-khimov
added
enhancement
smallhive
approved these changes
May 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With proper configuration this fixes our send.fs.neo.org problem when we have two containers involved in serving various parts of the website.